The story was relatively interesting, if a bit dry. The biggest problem I had with it was the lack of continuity with the rest of the series.

This book chronologically takes place a short time after Black Trillium. That would be fine if May and Norton had discussed it, but the lines of communication apparently failed.

If May knew how Norton was to conclude her story, she must have ignored it, because the character traits displayed by Kadiyah in Golden Trillium were not displayed by her in Blood Trillium.

Overall, I prefer the Kadiyah of Golden Trillium, to her through the eyes of May in Blood Trillium. I wish that something of that had been carried on.

The World of Three Moons did not seem the same world as that in the earlier works, or the later works. The appearance of the Sidonna didn't match the reference to them in the later works. It also did not have the strength of The Trillium due to the limited role of Haramis (maybe a paragraph), and the non-appearance of Anigel.

I do not think this is the best of Norton's work. If you are interested in the ongoing storyline of the World of Three Moons, you can safely ignore this book and miss none of that storyline. If you are an ANdre Norton fan, try to find it second hand.

I have to admit I've read better books than this. It was better than Black Trillium, which I found practically nauseating, but I read through Golden Trillium only because I kept thinking the plot would pick up a little. It never did-- at least not until the very end, where a novel's worth of conflict is squeezed into about two chapters.

If you managed to plow your way through Golden Trillium and/or Black Trillium, read Marion Zimmer Bradley's Lady of the Trillium--it's infinitely better. If you haven't read Golden Trillium yet, do yourself a favor and check it out of the library, so you won't feel cheated.

I liked this book a lot, I think It can easily be one of the best of the saga, the fact that Kadiya was the only triplet in the story troubled me a little but a part from that it was great!

Most of this book expands on topics of no interest to anyone who has a life. The prose is dense and hard to take. There are many technical details no one in their right mind would care about, even slightly.

You would think such a title would, at least, have its share of useful information. Trust me, it's slim pickings.

Out of 1160 pages of text, there are three on startup problems. Basically, you are told to start in Safe Mode. If you can't, good luck!

An example of the type of help you can expect is on page 20 of Chapter One (introductory material): "A value could tell you which interrupt and I/O port settings a piece of hardware uses. Suffice it to say that you'll find the value you need by using the keys, but you'll find the actual information you need by reading the values. There are three types of values: binary, string, and DWORD. Usually, only applications use the binary and DWORD value types. Values usually store configuration data in a format that can't be understood by humans."

I will modestly add, the way the early topics are explained is truly extraterrestrial. But for people who usually reside on this planet (as, I think, I do) this book is to be avoided. I kick myself for having wasted hours trying to follow the first two hundred or so pages.

This book would do well in a competition for the worst book ever written in the English language. I recommend it as a collector's item for that reason.

The authors got me up and running very fast. I didn't care all that much about details at first and this book avoided those details until later. The best thing it did at first was get me on the Internet with few hassles.

The power primers helped get my overloaded and underpowered system running better. I don't have the money to upgrade my system every few months, so getting the most out of what I have now is very important.

Once I did run into problems with my machine, the various theory and troubleshooting sections helped a lot. I found Chapter 15 especially helpful when I couldn't get games to run properly. The material on DirectX was great, even if it is a little out of date.

So, if you're looking for a book that's going to give you everything you need, try this one. I found that it really helped me when I needed it.

John Mueller and this book have saved me more hours of grief with Windows 95 than I could have imagined any one book would do. For example, when I needed some recommendation about how to keep my machine running correctly, I found everything I needed. There are sections on backup, regular maintenance like diagnostics and disk optimization, and some simple troubleshooting. I also found sections on the use of various files that other books don't even hint at. One such example appears in Chapter 9 where the author explains what the various compatibility files like Autoexec.bat are used for.

This book is a tad theory heavy, but even here the author excels. I now know how various parts of Windows 95 operate, making it much easier for me to diagnose problems with my system. The clear and easy to understand diagrams are a real plus. Again, the author lists filenames in the theory section. These file listings recently helped me fix a problem DLL (also known as DLL hell) by simply copying a new version of the DLL over the old one.

One of the authors, John Mueller, thoughtfully left his email address as part of the About the Author. I contacted him and found him extremely helpful and thoughtful of my concerns. Even though Windows 95 is old news, the author spent considerable time helping me use his book more effectively and even helped me around some problems areas within the book.

About the only two problems with this book are the index (not the author's fault since the publisher puts this together for him) and the lack of new hardware information. However, considering this book was put out before much of the modern hardware appeared on the scene, I can hardly blame the author for this oversight. My only thought is that he should keep the book up-to-date better for those of us who are still using Windows 95 and not filling Microsoft's pockets by buying Windows 98.

Sandra Gilbert's poignant tale of her 60 year old husband's death after prostate cancer surgery is marred by her universally distorted portrayal of his doctors at the UC Davis University Hospital, where he died in 1991. While she freely and repeatedly demonstrates her ignorance and lack of sophistication regarding the medical issues involved in her husband's case, that doesn't stop her from treating her misunderstandings and fantasies as reality. From her point of view, you would think that her husband's physicians were callous monsters, who didn't care if he lived or died. The truth is far less nefarious, though probably for her, less satisfying.

In the end, the real events surrounding her husband's death do not reveal any conspiracy, cover-up, or gross negligence. In fact, her husband suddenly "crashed" only after what was essentially over 4 uneventful hours in the recovery room, where the only abnormality was a low grade elevated heart rate (common after surgery) and a one time drop in blood pressure early on, which responded immediately to appropriate treatment (also common). Indeed, until he coded, he appeared to be doing quite well. It is only after the failed resuscitation that it became apparent that he must have been bleeding occultly, despite his apparent hemodynamic stability. The bottom line is that everyone in the recovery room missed the fact that that he was hemorrhaging internally, not because they were indifferent or incompetent, but because the clues were so subtle and their level of suspicion was too low.

She complains that no one was forthcoming with information, as she struggled to understand what happened, yet, with her own words, whenever the primary surgeon tries to discuss the case, before and after the surgery, she demonstrates that she has trouble understanding the simplest concepts, even though he speaks in plain everyday language. Instead, she offensively ridicules his accent, and follows every statement of his with her own italicized confused thoughts and fantasies. Almost every statement or appearance of a physician in this book is caricatured and editorialized.

In the end, she opts to take the money, accepting a settlement, rather than continue with depositions and go to trial, insuring that she never gets the explanation she claims she wants and needs so badly.

If there are villains here it is her friends and family. For example, after her husband's death, a couple comes up to her and with the same breath as they ask "What happened?", they announce that a lawyer friend has told them that she has a case for medical malpractice. How in the world would he know? There are so many self-appointed "experts" among her relatives and acquaintances, all whispering in her ear their own theories and rumors and offering advice. And there is so much cynicism and anger among her family and friends toward the doctors, you would have thought they had bodily thrown her husband out a hospital window to his death. Indeed, that is how his care is ultimately described.

There is much made of a missing hematocrit, drawn after an hour in the recovery room, yet it is acknowledged that hematocrits can be misleading because of the time required for "equilibration." She also makes much of an inability of the anesthesiologists to intubate her husband, which aborted the first attempt at surgery. His pictures in the book show him to have been a stocky man with a receding chin, short neck, and full beard. Of course they had trouble! There is no guarantee that you can successfully intubate any patient, even if you know ahead of time it will be difficult. They did the right and safe thing, by canceling the case, yet she repeatedly revisits the failed intubation and prudently cancelled case, each time more vehemently, until she ultimately claims her husband began to die then and there!

Mrs. Gilbert revels in the role of victim, but like so many that title becomes comforting only if there are villains. And if there are none, she and her family, friends, and lawyers will manufacture them. Indeed, mistakes were made, with disastrous consequences, but there is no evidence that her late husband was treated with anything but professional kindness, charity, and compassion. Maybe his doctors deserve a little too.

This book is hardly about wrongful death. It is the story of one person's attempt to deal with the sudden and unexpected death of a spouse. Certainly there are some elements of the wrongfullness of the death of her husband portrayed in the book. However, the author is primarily focused on her own pain, suffering and inability to deal with the death and subsequent activities.

One most definitely has sympathy with the author and her family for their loss. The writing is a celebration of the misery brought on by the death. A similar tale could be told of any sudden and unexpected death of a loved one.

Our mother was diagnosed in the late 80's with the worse types of rheumatory arthritis ever and began walking with a cane as her primary complaint was the pain in her right hip. She was also an adamant smoker and in Dec. 97 was diagnosed with a cancerous spot on her lung. Her doctor wanted to do surgery stating she wasn't going to die; all the time ignoring her repeat requests for attention to her hip. He stated he wanted to take care of the problem at hand then he would deal with the hip. The middle of Feb 98 she expired and was, by the grace of God, brought back to life. Consequently, it was all over, as her hip bone was completely eaten up when they discovered bone cancer as it had matasized all through her body. She passed the 19th of Mar 98. During the first discovery of the cancer the doctor did an MRI and through the latter part of her life, kept ignoring repeated requests to deal with that hip. She suffered through this cancer thinking it was arithritis. A major part of the illness was pneumonia and continuous upper respiratory infections. I must mention that I live in Ga. and the other 5 siblings in Va and Md. Mother live in Pa. and would not move as she loved Pa. Of course, this made it difficult to track her and assist her in monitoring her visits to the doctor. Mother was always the type of woman who like to keep her "business" to herself; always an organized person. We have since tried, to no avail, to get an attorney to prove his negligence. I am still looking for someone to go over, verbatim, her medical records. To my knowledge, there has been no mention of her need to quit smoking. We, the family, also believe we have a case against the cigarette company.

If you want a complete history of the Microsoft operating system, this is the book for you. It also gives a overview of the system and can help you see how the parts are connected. Unfortanetly, it seems to be written for someone who is upgrading from DOS V.1. The authors seem most concerned with getting old DOS programs and old hardware to work in Windows 98 and assume that anyone with new components and windows programs will never have a problem. This is not true!

The book assumes you are already familier with the old diagnostic tools. For example, it tells you that the untility Dr Watson is much improved but only hints at what the utility does and gives no instruction for using it. (you will not find Dr Watson on the start menu so new users will not be able to even open it.)

I bought the book mainly because I have a software problem with my new computer. This book told me about starting in safe mode and went on to say that if that did not work the problem could be very difficult to track down. Thank you Mr Norton.

Fortanetly.

Despite the fact that Millenium and Win2K have been released, for support folks the version of Windows we most often encounter is still Win98. This book has just about everything you need to know about Windows 98 right there between the covers.

Unlike one of the other previous reviewers, I found the background and theory portions of the book to be incredibly useful in figuring out just what has gotten out of whack with a system that is giving me fits. The explanations of memory usage, peripheral drivers, and FAT32 should be required reading for anyone who does more than word processing on their computer.

The plus of buying this book is that you get a lot of useful information. There were few questions that I couldn't answer by reading a bit. I found that the information was much better organized than the Microsoft documentation and more complete as well.

In addition, the author provides really good productivity tips that have made working with Windows a pleasant experience. I usually don't have a lot of time to waste getting things done, so anything that helps me work more efficiently is welcome.

The big negative for this book is that the author spends a lot of time discussing theory. He'll talk about how things work for pages at a time. While this is OK if you have a lot of time to read, it's time consuming to dig through pages of theory to find the one piece of useful information you need. I did find the theory useful, so I can't say the author was completely wrong in adding it to the book, I just wish all of the theory had been included in separate sections so I could ignore it.

I gave the book five stars because it is an essential reference despite the organizational flaws. Any book that can fix as many problems as this one can deserves high marks. Perhaps the author will include less theory the next time around.

Like other reviewers I hoped to get more out of the sequel after reading Shadow of Albion, and I like Edghill. But the paperback, even with fewer footnotes, was hard going.
The threads never came together satisfactorily and the plot was ridiculous. I don't mind christianity vs satanism in a book butin this one it made the characters extremely one-dimensional and just didn't gel with the magic mixed with voodoo.
How is Sarah supposed to prevent the People's decimation with or without the Sahoya's help? Why is the chief's son courting her? What exactly did the Grail do? The book raised loads of questions and answered none--the authors would have done better taking out most of these plot devices.
I'll read other books by both authors--just not the ones they co-author.

Is it a bad sign that I just finished this book the night before last, and now I'm hard-pressed to remember much of the plot?

This book's predecessor, _Shadow of Albion_, was fun in a light sort of way, with the promise of sequels that would delve deeper into the faery magic at which it hints. I should have gotten my first clue about _Leopard in Exile_ when I looked at the cover art. Thomas Canty's drawings are lovely as always, but this illustration looks like it's supposed to be a rough preliminary sketch, compared to the sublime cover of _Albion_. Even the typefaces are clunkier. But I tried not to judge the book by its cover.

Inside, though, I found little of interest. I had hoped that the characters, who were kind of cardboard in _Albion_, would get fleshed out now that we're getting to know them better. Nope, still cardboard. It's even worse in this one because people are going around moping about how much they love their husband/wife and yet the relationship has not been developed in the story. Why do they love each other? Because the authors say so, I guess. And to add more frustration, the authors seem to be under the impression that a good plot can be obtained simply by continually landing the characters in danger. (It reminds me of a 70s bodice-ripper I read years ago, in which the heroine got raped, then shipwrecked on a tropical island, THEN kidnapped by pirates, THEN trapped in an opium den... You get the idea.) Dropping the characters into one problem after another works pretty well if we KNOW the characters and CARE what happens to them, but since they're still 2-D, the constant action keeps us from learning any more about them. It's just crisis after crisis after crisis, and seldom a conversation. Not to mention, the magic doesn't get explained! Sarah went to the New World to fulfill a promise to the Fair Folk, but then they were absent for the first nine-tenths of the book, then showed up just long enough to give Sarah some vague aid against the villain, then disappeared again, without any explanation.

I don't know if I'll read the third Carolus Rex book. I know both Norton and Edghill are capable of better books than this. Let's hope they remember that.

I wasn't really intending to review this book, but I kept writing one as I read it, so:

Negatives:
1. The footnotes were QUITE condescending. Fortunately they were dropped after the first chapter in the paperback version, or this book would have quickly become wall-thumping material.

2. The characters are painfully flat. Wessex is a character out of a cut-rate Regency romance; I would have accepted him that way if the book WAS a Regency romance, but this is Andre Norton. Many of the characters have only one or two major traits and grow boring quickly (read: Robie, the Sahoya, etc.).

3. The plot was clunkly and terrible. Also the opening scene of d'Charenton was disgusting beyond need. I really don't feel it was necessary to peg him as "evil," most people have heard of the Marquis de Sade. (Or if we haven't I'm sure Edghill would be happy to tell us about him).

The postitive:
1. If you skim through certain bits of the novel, the pacing is quite fast. I mostly found myself wishing that the book was over and that they would not write another, but I find that my wishes will not be granted--they intend to write a third.

I honestly meant to give this book three stars, but now that I think over it, it is a two star book. I really hope the third doesn't actually get put out. I COULD have read a cheap Regency and been just as satisfied with the result, maybe even more so because the clunky plot devices would be thankfully absent. There are much better books that combine the topics of the Regency and magic, and any reader would do well to pick up one of these instead.

I found this book...and the discussion of error trapping isgreat, better than I've found elsewhere.

Amazon's author listing is not right: the authors listed inside the book are Peter Norton, Harold Davis and Phyllis Davis. The Norton book on each VB version has a different set of authors, so it is not clear that the same quality always applies.

A great deal of VB has to do with Forms and Controls, which are discussed but are not my point of view. I like this book because of Chapter 4: Programming in VB. This chapter gives a very concise and clear summary of all the language features under the rubric "What's still BASIC in Visual Basic?" Chapter 4 also includes class modules, and some more details are given later in Chapter 14 in an example that controls Excel from VB. I also appreciated Chapter 12: Error-Handling and Debugging, which explains both coding with the On Error feature of VB, as well as the use of the VB debugging tools.

These items comprise about 1/10th of the book. But because of its age I found this book for much less than its original price, which made the book worthwhile even so.

I would recommend this book for studying with instructor, not by yourself. It introduces some of the concepts in a rather quick manner without giving you the in-depth introduction to the topic. I taught couple of people VB and I find that Norton's is very helpful for the students, but as I have mentioned, you need instructor's guidance with it.

The first chapter is fast paced and exciting; probably written by Norton, who left the rest of the book to the junior author. The remainder of the book drags on and on, with no character development, no interesting fantasy evironment, no action, and really nothing to recommend it.

I picked this book up because I had enjoyed Norton's writing in the past. Unfortunately, I was sorely disappointed by the book. The plot was interesting--if unoriginal--and the book had some cute parts to it. However, the writing style was juvenile at best. The book often seemed more like a plot summary than a novel, so that the authors were able to skim through the events of several decades in 244 pages. The book was told from the point of view of several characters over the span of about 40 years, giving the book a disjointed tone. None of the characters was ever really developed, and most of the villains were incredibly shallow. The ending was anticlimactic and inconclusive. The authors often left out even incredibly basic descriptions, so that I often didn't know what characters looked like. All in all, I had the impression that the authors didn't like the book very much and were trying to get through it as quickly as possible. If they had filled it out properly, or made it into two full novels, it might have been worth the paper it was printed on. The book might be appropriate for adolescent readers, but adult readers might want to look for something a little bit better.

Oh yes, exactly! I, I suppose in contrast to those prior in reviews, LOVED this book incredibly. While I DO wish that Cee's story was expanded upon (towards the end it seemed a little rushed) I still can't wait for a sequel! I'm now reading the "Chronicles of Witchworld," and wish most desperately I could find a sequel on the story of Ciara's granddaughter.

How I treid to finsh it! I couldn't get past the first 70/80 pages or so. the only part that interested me was Irasmus. I wanted to find out more about him and his thoughts. The narrative is sometimes confusing and it is hard to empathize with the characters. It is very hard to get ino the book

ok, i was very unhappy with what other people wrote. but i respect their opinions. i admit that it was very dense, and the names sometimes got confusing, but it is a really good book. at first i was intrigued by the simplicity of it's description on the back, (i needed summer reading and i love fantasy) so i bought this book.
at first i had a lot of trouble, because it is a style that is hard to read, but i got used to it, and i really enjoyed the plot and the overall ending. i was very satisfied, so much so that after tearing apart my room and realizing i had lent my copy to an ex-best friend and never got it back, i am going to by a new one!!
happy reading! and just try the book, it's really good once you get into it!

I have read the rest of the reviews impatiently .Wind in the Stone is a perfectly good book.True ,it begins slow ,true Norton did put some pointless stuff in it ,but overall it was good.At first I thought it would be horendous as the previously written book ,Scent of Magic,but it was fine.As I always do when I read one of Norton's best ,I enjoyed the creatures that Norton invented .Especially the Sasqua and the gobbes.Her villain is hateable ,her characters loveable,the plot enchanting .Here is the plot :Irasmus ,the evil magician assaults the valley with his gobbes.The Dark was driven out long ago by the Wind (in this book Wind is a powerful substance)but now it has returned .Irasmus brutally attacks a family with a woman with two twins,one boy one girl .Irasmus catches the boy but not the girl .The girl ,Falice flees into the wood with her Mother .Her Mother dies but she lives and is adopted by the Sasqua,the inhabitants of the wood .When she grows into a young woman ,the Wind tells her that she must overthrow Irasmus and free her brother.

This book is boring. It has a wonderful IDEA for the plot but Norton over-embellished and as a result, you find yourself reading about dark dank halls and the numerous sub-plots. It's as if the main plot finally figured out it wasn't being paid attention to and it ran away from it's abusing master.

Most reviews of this book were to say the least bad. I however enjoyed it. it was what I like to call brain candy. YOu don't have to think hard to read it. You just enjoy it. If you like Andre Norton's works, this is not her best effort, but it is a fun and quick read to pique further interest into scifi/fantasy reading for someone just starting to develop a taste for it. BTW, I wouldn't reccommend this for a guy. This was definitely a chick book.

I think that anyone who says that this book isn't good is a true lover of fantasy. The plot was great and well-developed, the characters strong and the scenery fantastic. It was the first book I've read by Norton and I am now a great fan of hers! I know a good book when I read it and this was definitely one of them!

This book is utterly AWFUL when it comes to comparing it with other academic histories. I would not recommend it to anyone, except as one of the worst histories written, EVER.

By Mary Beth Norton. Founding Mothers and Fathers: Gendered Power and the Forming of American Society. (New York: Alfred A. Knopf, 1996, hardcover 1996. Pp. ix, 496, appendix, abbreviations, notes, index....hardcover.)

From the time of the Pilgrims to present day, women have played more of a substantial role than they are commonly accredited for. In Founding Mothers and Fathers: Gendered Power and the forming of American Society, Mary Beth Norton parlays her idea that although woman did not have an independent role in the political arena of early American society there were many woman and groups of woman who knew the undisclosed sins of the community. This they used in the assumption of leadership roles among the communities.
Norton goes on to explain power inside the household as well as in the community. She connected Sir Robert Filmers' (The Filmerian view) and John Lockes' philosophies (the Lockean view) to both domestic life and the political structure and formation of early American society.
As you probably know, the practice of bearing children was most likely the primary focus of 17th century colonial woman. Lacking in birth control, a woman would go through a constant cycle of becoming pregnant and giving birth. Norton points out that these regular childbearing sessions excluded men from attending. It is very important to understand the role of the midwife. She could be the necessary one in keeping the woman and child alive during birth. She could, as well, expose any form of bastardization, premarital sex, adultery, and infanticide. The power of the midwives and the ignorance of men on the subject of childbearing gave way to many cases in which women could bend around the "man-made" laws.
It is probably demeaning these days to say that woman "gossip." Well, according to Norton, this did indeed go on during colonial times. The reader will discover the "gossip networks." Due to the fact that woman were separated from men in many social aspects led to these networks. Rumors of criminal activities would travel this way to the Colonial Magistrate and would very often result in punishment for the crime.
I found the two different philosophies on gender power to be very interesting. Should the most power come from the parent most represented, whichever that may be? This idea would bring more power to widows and present them with a greater role in the community. However, the people of this enlightened area would demand that the power of a woman's authority was inexistent outside the home.
Mary Beth Norton is a very accredited historian. This book gives remarkable incite to the power of woman in colonial times. Anyone interested in the social history of our country would enjoy this book and feel enriched after reading it. Many of the woman's roles discussed were unknown to me. Norton puts them across in a very intelligent and unquestionable way using many actual cases of the times to back up her theories.
This book, although written by a scholarly author, is not a difficult reading. Since it deals with many aspects of colonial life unknown to many people the readers interest should withstand through its entirety. Indeed, woman played an immense, although not formal or independent, role in the formation of our country as it is today.
-Charles Michael Farley-

Norton argues that during the mid to late 17th century, colonial American political authority was based on biblical interpretations which encouraged a unified, gender-power based authoritarian system centered on the role of the father as undisputed ruler of his household. The founders were operating in a "Filmerian system" in which the sources of authority in the state and family were identical.

However, this Filmerian system did create opportunities for women to wield some power. High-ranking widows were the rulers of their households and were deferred to by both males and females of lower ranks. Problems arose when these high-ranking widows failed to fall in with the male consensus, such as Anne Hutchinson.

In the Chesapeake region, the Filmerian system was much less successful than in New England because the Chesapeake settlers were predominantly single men. The family-based power system failed in this region because it had very few traditional family households. Although power remained gender-based in the Chesapeake region, it became more like a "Lockian system" in which power in the family was differentiated from political power.